[Snyk] Upgrade @opentelemetry/sdk-metrics from 1.23.0 to 1.25.1 #677
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @opentelemetry/sdk-metrics from 1.23.0 to 1.25.1. See this package in npm: @opentelemetry/sdk-metrics See this project in Snyk: https://app.snyk.io/org/p0nder0sa/project/07a6ccc2-f67f-412b-96dd-48a12d46c46a?utm_source=github&utm_medium=referral&page=upgrade-pr
gregory-j-baker
approved these changes
Jul 30, 2024
|
Closing. This update was rolled into #676. |
gregory-j-baker
deleted the
snyk-upgrade-84b8e4a3a784e7a11ad67ef057d7cb37
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @opentelemetry/sdk-metrics from 1.23.0 to 1.25.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 4 versions ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: @opentelemetry/sdk-metrics
-
1.25.1 - 2024-06-20
- refactor(examples): added usage of @ opentelemetry/semantic-conventions and @ opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @ Zen-cronic
- refactor(context-zone-peer-dep): use explicit exports #4785 @ pichlermarc
- refactor(context-async-hooks): use explicit exports #4785 @ pichlermarc
-
1.25.0 - 2024-06-05
- feat: support node 22 #4666 @ dyladan
- feat(context-zone*): support zone.js 0.12.x #4376 @ maldago
- refactor(core): Use tree-shakeable string constants for semconv #4739 @ JohannesHuster
- refactor(shim-opentracing): Use tree-shakeable string constants for semconv #4746 @ JohannesHuster
- refactor(sdk-trace-web): Use tree-shakeable string constants for semconv #4747 @ JohannesHuster
- refactor(sdk-trace-node): Use tree-shakeable string constants for semconv #4748 @ JohannesHuster
- refactor(sdk-trace-base): Use tree-shakeable string constants for semconv #4749 @ JohannesHuster
- refactor(resources): update deprecated semconv to use exported strings #4755 @ JamieDanielson
- refactor(exporters): update deprecated semconv to use exported strings #4756 @ JamieDanielson
- refactor(examples): use new exported string constants for semconv in examples/esm-http-ts #4758 @ Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/basic-tracer-node #4759 @ Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/http #4750 @ Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/grpc-js #4760 @ Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/otlp-exporter-node #4762 @ Zen-cronic
- refactor(examples): use new exported string constants for semconv in examples/opentracing-shim #4761 @ Zen-cronic
-
1.24.1 - 2024-05-07
- fix(core): align inconsistent behavior of
- fix(resources): prevent circular import (resource -> detector -> resource -> ...) #4653 @ pichlermarc
- fixes a circular import warning which would appear in rollup when bundling
- fix(exporter-metrics-otlp-grpc): add explicit otlp-exporter-base dependency to exporter-metrics-otlp-grpc #4678 @ AkselAllas
-
1.24.0 - 2024-04-24
- feat(sdk-trace-base): log resource attributes in ConsoleSpanExporter #4605 @ pichlermarc
- feat(propagator-aws-xray): moved AWS Xray propagator from contrib 4603 @ martinkuba
- feat(resources): new experimental detector ServiceInstanceIdDetectorSync that sets the value for
- fix(sdk-trace-web): fix invalid timings in span events #4486 @ Abinet18
- fix(resources): ensure BrowserDetector does not think Node.js v21 is a browser #4561 @ trentm
-
1.23.0 - 2024-04-03
- perf(sdk-trace-base): do not allocate arrays if resource has no pending async attributes #4576 @ Samuron
- feat(sdk-metrics): added experimental synchronous gauge to SDK #4565 @ clintonb
- this change will become user-facing in an upcoming release
- fix(sdk-metrics): increase the depth of the output to the console such that objects in the metric are printed fully to the console #4522 @ JacksonWeber
from @opentelemetry/sdk-metrics GitHub release notes1.25.1
📚 (Refine Doc)
🏠 (Internal)
1.25.0
🚀 (Enhancement)
📚 (Refine Doc)
1.24.1
🐛 (Bug Fix)
getEnv()andgetEnvWithoutDefaults()when aprocesspolyfill is used #4648 @ pichlermarcgetEnvWithoutDefaults()would useprocess.envif it was defined when running in a browser, whilegetEnv()would always use_globalThis. Now both use_globalThiswhen running in a browser.@ opentelemetry/resources1.24.0
🚀 (Enhancement)
service.instance.idas random UUID. #4608 @ maryliag🐛 (Bug Fix)
1.23.0
🚀 (Enhancement)
🐛 (Bug Fix)
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: